Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd39aec7d60e2353ffc73646a1c31d5808b7faea4033cb806307015de4614e36

Tx prefix hash: 51f78ca0c0a34025a629f0c144ecbe5e51d99842614c5efb8870d24dbf131959
Tx public key: 95fe82e48355260fd16273587767de38e84d2858c3d8e80dc9bf4d8294d063f9
Timestamp: 1694778698 Timestamp [UCT]: 2023-09-15 11:51:38 Age [y:d:h:m:s]: 01:236:12:12:21
Block: 848639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430145 RingCT/type: yes/0
Extra: 0195fe82e48355260fd16273587767de38e84d2858c3d8e80dc9bf4d8294d063f90211000000084b8f5122000000000000000000

1 output(s) for total of 0.946469808000 dcy

stealth address amount amount idx
00: 95da5fe1e719f7d1f134c59cee3a7f73cb1eb8cc91623c117b6a4511698db1df 0.946469808000 1302255 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 848649, "vin": [ { "gen": { "height": 848639 } } ], "vout": [ { "amount": 946469808, "target": { "key": "95da5fe1e719f7d1f134c59cee3a7f73cb1eb8cc91623c117b6a4511698db1df" } } ], "extra": [ 1, 149, 254, 130, 228, 131, 85, 38, 15, 209, 98, 115, 88, 119, 103, 222, 56, 232, 77, 40, 88, 195, 216, 232, 13, 201, 191, 77, 130, 148, 208, 99, 249, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8