Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b9781944e5de6af340c52ff4285e200b7490a96eb302f852f448e47ab2ac86d

Tx prefix hash: ce37b236ea8736a96d5bc5f1dcf2ae49e09722f084f120aa14475f2133b63994
Tx public key: 74c0aed9b705ecd2e4f895cee44dee3040b91204fb8562bfe83ee21f30d6c376
Timestamp: 1759581068 Timestamp [UCT]: 2025-10-04 12:31:08 Age [y:d:h:m:s]: 00:096:02:02:47
Block: 1382583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68812 RingCT/type: yes/0
Extra: 0174c0aed9b705ecd2e4f895cee44dee3040b91204fb8562bfe83ee21f30d6c376021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f32209dce223f9c4d226802b06ee689ad286975eb6b614e2e33e029e101b8f6 0.600000000000 1870718 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": 1382593, "vin": [ { "gen": { "height": 1382583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f32209dce223f9c4d226802b06ee689ad286975eb6b614e2e33e029e101b8f6" } } ], "extra": [ 1, 116, 192, 174, 217, 183, 5, 236, 210, 228, 248, 149, 206, 228, 77, 238, 48, 64, 185, 18, 4, 251, 133, 98, 191, 232, 62, 226, 31, 48, 214, 195, 118, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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