Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e21cd527dd37f993d9d27170ead4b977cb4154756108b447070ddbace381990

Tx prefix hash: e2613a11273f4dd59507991bcb268b952a1a8148d3d5cd6c628ae8c2e1365c4a
Tx public key: 90a65b95b3907b8ed61c10f75aa649e04f4701e2194fbdd63d677f235ebe3013
Timestamp: 1580783435 Timestamp [UCT]: 2020-02-04 02:30:35 Age [y:d:h:m:s]: 05:006:12:16:37
Block: 57997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156860 RingCT/type: yes/0
Extra: 0190a65b95b3907b8ed61c10f75aa649e04f4701e2194fbdd63d677f235ebe30130211000000034943cd9f000000000000000000

1 output(s) for total of 394.305363504000 dcy

stealth address amount amount idx
00: 9b7086deb7aaf3055fb1a3e1aac30f2c79bbcaf360e4350042fbd3a61f1b4f2a 394.305363504000 107270 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": 58007, "vin": [ { "gen": { "height": 57997 } } ], "vout": [ { "amount": 394305363504, "target": { "key": "9b7086deb7aaf3055fb1a3e1aac30f2c79bbcaf360e4350042fbd3a61f1b4f2a" } } ], "extra": [ 1, 144, 166, 91, 149, 179, 144, 123, 142, 214, 28, 16, 247, 90, 166, 73, 224, 79, 71, 1, 226, 25, 79, 189, 214, 61, 103, 127, 35, 94, 190, 48, 19, 2, 17, 0, 0, 0, 3, 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