Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71dad68acd495509bcbd1807a27cbe80aa68d27f5845bebf78ff47031434457

Tx prefix hash: e2b16464a07655f1254b037034dce56d963e4b644502e5d2aab4d3a5ebfa724f
Tx public key: e6d6ab18930d0904e303c357e0801bf802ff575acbbeaae98b2c10c0fad8c531
Timestamp: 1707914107 Timestamp [UCT]: 2024-02-14 12:35:07 Age [y:d:h:m:s]: 01:106:02:38:23
Block: 957345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336934 RingCT/type: yes/0
Extra: 01e6d6ab18930d0904e303c357e0801bf802ff575acbbeaae98b2c10c0fad8c5310211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd11e5de1b3314658f4c32f1b43067afaf4dc9f6becb800033f9c36c7a73baaa 0.600000000000 1416663 of 15

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": 957355, "vin": [ { "gen": { "height": 957345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd11e5de1b3314658f4c32f1b43067afaf4dc9f6becb800033f9c36c7a73baaa" } } ], "extra": [ 1, 230, 214, 171, 24, 147, 13, 9, 4, 227, 3, 195, 87, 224, 128, 27, 248, 2, 255, 87, 90, 203, 190, 170, 233, 139, 44, 16, 192, 250, 216, 197, 49, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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