Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34456de46038eaad6a175a0d2b405fb210c2595b4cefd9847f922ca02fdb4678

Tx prefix hash: 601d73fa5dc005f07e831bbffd4cf3eff2d2523b18a87814c3d318b01863f77c
Tx public key: 13bdd9e162d307335ef06ec20ea1fdb2e5d936417bc0105abd894cff436f968b
Timestamp: 1743937677 Timestamp [UCT]: 2025-04-06 11:07:57 Age [y:d:h:m:s]: 00:229:03:56:46
Block: 1255512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161508 RingCT/type: yes/0
Extra: 0113bdd9e162d307335ef06ec20ea1fdb2e5d936417bc0105abd894cff436f968b0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a733481fb6c58c26e4a7827ce833cbaebd1b9bd39fac346798a7b876f9a11218 0.600000000000 1742617 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": 1255522, "vin": [ { "gen": { "height": 1255512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a733481fb6c58c26e4a7827ce833cbaebd1b9bd39fac346798a7b876f9a11218" } } ], "extra": [ 1, 19, 189, 217, 225, 98, 211, 7, 51, 94, 240, 110, 194, 14, 161, 253, 178, 229, 217, 54, 65, 123, 192, 16, 90, 189, 137, 76, 255, 67, 111, 150, 139, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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