Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c6b17f0bb967ca09ed6fdd2ececf649fd158eada8da7fe662c4f3a0fa0388c7

Tx prefix hash: c5a4b02b828a29102f12e0d5d0571d4bcaa9f29af393e848e117d89f64d1a7b8
Tx public key: bcbe8803b74d9c184196a801794ec8703222b3046d45cb6d5a58fab36d343ebc
Timestamp: 1736225855 Timestamp [UCT]: 2025-01-07 04:57:35 Age [y:d:h:m:s]: 00:070:02:48:11
Block: 1191938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49893 RingCT/type: yes/0
Extra: 01bcbe8803b74d9c184196a801794ec8703222b3046d45cb6d5a58fab36d343ebc0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6efe99b42841a06be1568095e36246c23cd0a458024f924908c65bc3b7cbac2c 0.600000000000 1678481 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": 1191948, "vin": [ { "gen": { "height": 1191938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6efe99b42841a06be1568095e36246c23cd0a458024f924908c65bc3b7cbac2c" } } ], "extra": [ 1, 188, 190, 136, 3, 183, 77, 156, 24, 65, 150, 168, 1, 121, 78, 200, 112, 50, 34, 179, 4, 109, 69, 203, 109, 90, 88, 250, 179, 109, 52, 62, 188, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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