Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b513d83e4232f7ccf5738185e004dff3bed1d436ff9f3b2d2e6b0903adb8941a

Tx prefix hash: 08c81a6d4ed4eabb05686b9def922e938ad572166c93faa4ab4b31a52624bfe7
Tx public key: 8484fd4f0af37fca66993e9d4f327c2b896ab746ce12d2df0fab03ba3c1b864f
Timestamp: 1582443799 Timestamp [UCT]: 2020-02-23 07:43:19 Age [y:d:h:m:s]: 04:308:05:10:21
Block: 70850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112775 RingCT/type: yes/0
Extra: 018484fd4f0af37fca66993e9d4f327c2b896ab746ce12d2df0fab03ba3c1b864f02110000000256c366d3000000000000000000

1 output(s) for total of 357.486785382000 dcy

stealth address amount amount idx
00: 803f2cf815f4d7ffb494cccfb14fff45aa9622134904dc371d68fd25e416bd6a 357.486785382000 130872 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": 70860, "vin": [ { "gen": { "height": 70850 } } ], "vout": [ { "amount": 357486785382, "target": { "key": "803f2cf815f4d7ffb494cccfb14fff45aa9622134904dc371d68fd25e416bd6a" } } ], "extra": [ 1, 132, 132, 253, 79, 10, 243, 127, 202, 102, 153, 62, 157, 79, 50, 124, 43, 137, 106, 183, 70, 206, 18, 210, 223, 15, 171, 3, 186, 60, 27, 134, 79, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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