Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3941b3cfe9c49ec98ff66252650ecf12a04bbcb8d1366adafa0b7ac37284b646

Tx prefix hash: 5b4768ae00a4e85c5e1c96ae7adb748956f97bcfb8c3236823e3c1fd43955454
Tx public key: af2672e70677961d90cc607ca007bead9ca381338eb4b40d7423b0d1bb8f9de7
Timestamp: 1584519338 Timestamp [UCT]: 2020-03-18 08:15:38 Age [y:d:h:m:s]: 04:254:06:12:21
Block: 84802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077376 RingCT/type: yes/0
Extra: 01af2672e70677961d90cc607ca007bead9ca381338eb4b40d7423b0d1bb8f9de70211000000044943cd9f000000000000000000

1 output(s) for total of 321.378303551000 dcy

stealth address amount amount idx
00: a078fb95fd1d145db0a1c4bf3cfa767299d8716ea4fd8223b4efd3b3e3aa565a 321.378303551000 153530 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": 84812, "vin": [ { "gen": { "height": 84802 } } ], "vout": [ { "amount": 321378303551, "target": { "key": "a078fb95fd1d145db0a1c4bf3cfa767299d8716ea4fd8223b4efd3b3e3aa565a" } } ], "extra": [ 1, 175, 38, 114, 231, 6, 119, 150, 29, 144, 204, 96, 124, 160, 7, 190, 173, 156, 163, 129, 51, 142, 180, 180, 13, 116, 35, 176, 209, 187, 143, 157, 231, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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