Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05e6f1d43186c050de5880159c07a6758480a0016b607c9e656e602ad6de7d8

Tx prefix hash: 658b239214b53dd27534762525a1cc24c2a7177629dd5ab9f0fa31a6fd14841d
Tx public key: 3a5a85a2c75866f7a55453f5b7561328df1d7d490e7b44d5686c1a82388b9a75
Timestamp: 1700472576 Timestamp [UCT]: 2023-11-20 09:29:36 Age [y:d:h:m:s]: 01:128:14:33:56
Block: 895669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353066 RingCT/type: yes/0
Extra: 013a5a85a2c75866f7a55453f5b7561328df1d7d490e7b44d5686c1a82388b9a750211000000024b8f5122000000000000000000

1 output(s) for total of 0.661114653000 dcy

stealth address amount amount idx
00: 63057f5c884bb076cd54120f8867991cecc92cd637cae4ea881198f6b89afce4 0.661114653000 1351910 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": 895679, "vin": [ { "gen": { "height": 895669 } } ], "vout": [ { "amount": 661114653, "target": { "key": "63057f5c884bb076cd54120f8867991cecc92cd637cae4ea881198f6b89afce4" } } ], "extra": [ 1, 58, 90, 133, 162, 199, 88, 102, 247, 165, 84, 83, 245, 183, 86, 19, 40, 223, 29, 125, 73, 14, 123, 68, 213, 104, 108, 26, 130, 56, 139, 154, 117, 2, 17, 0, 0, 0, 2, 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