Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4273817bc8755c16f154cb864ffe0b3fb61e9edb602a00d198ad5dc35f8c735c

Tx prefix hash: 919369d800d08cbc74fc45d34f3a372a11ccc7a4b7afa25b7d2603fe53c87f2e
Tx public key: 2ef7480a98b7fb24adbefe6935517dc7dd3f5fb65050b3eadaae24b3fabf2d92
Timestamp: 1736453198 Timestamp [UCT]: 2025-01-09 20:06:38 Age [y:d:h:m:s]: 00:160:01:13:23
Block: 1193820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114086 RingCT/type: yes/0
Extra: 012ef7480a98b7fb24adbefe6935517dc7dd3f5fb65050b3eadaae24b3fabf2d920211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1af89ea63479250b2947ce4ed0f3fe8cc0a17136116986fb1a55386a4f0af24e 0.600000000000 1680385 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": 1193830, "vin": [ { "gen": { "height": 1193820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1af89ea63479250b2947ce4ed0f3fe8cc0a17136116986fb1a55386a4f0af24e" } } ], "extra": [ 1, 46, 247, 72, 10, 152, 183, 251, 36, 173, 190, 254, 105, 53, 81, 125, 199, 221, 63, 95, 182, 80, 80, 179, 234, 218, 174, 36, 179, 250, 191, 45, 146, 2, 17, 0, 0, 0, 4, 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