Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e3effdd84d9b95c848eaa8ef8c40375a817f3bac81c485e575b8100e5dce4e2

Tx prefix hash: 8a54deb83a35cd70eaec102c4a4afd40966bd0c107f6be1879c937029fddf8d0
Tx public key: 932a07800e83e9360cda2c98c5af54e06aebe06edbbfdc3d1817d28b3b926286
Timestamp: 1707859247 Timestamp [UCT]: 2024-02-13 21:20:47 Age [y:d:h:m:s]: 01:057:02:16:21
Block: 956905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301838 RingCT/type: yes/0
Extra: 01932a07800e83e9360cda2c98c5af54e06aebe06edbbfdc3d1817d28b3b92628602110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 943752e10f5dc375d1a828d7509e2bc7f337bed175b94fc22747ede302ae6ca5 0.600000000000 1416217 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": 956915, "vin": [ { "gen": { "height": 956905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "943752e10f5dc375d1a828d7509e2bc7f337bed175b94fc22747ede302ae6ca5" } } ], "extra": [ 1, 147, 42, 7, 128, 14, 131, 233, 54, 12, 218, 44, 152, 197, 175, 84, 224, 106, 235, 224, 110, 219, 191, 220, 61, 24, 23, 210, 139, 59, 146, 98, 134, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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