Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacae43bd8f39c3262f6ca524c9430068a30d1d5643c338d319bf6576eac0d22

Tx prefix hash: fb0633baaad8cfb1674a229cfa1bd9e2f7584b9cda7e2d93d3165e0a0cfdc197
Tx public key: b872183de7c1a2aae5bd3a46692d596e256d746a94680ee2fac3d41b4fac85a7
Timestamp: 1761396490 Timestamp [UCT]: 2025-10-25 12:48:10 Age [y:d:h:m:s]: 00:073:08:57:46
Block: 1397642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52529 RingCT/type: yes/0
Extra: 01b872183de7c1a2aae5bd3a46692d596e256d746a94680ee2fac3d41b4fac85a70211000000075dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff0bf26f38104e192279f0dd6e77a29537f034347dc2c8a11aad6b6595d09254 0.600000000000 1885933 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": 1397652, "vin": [ { "gen": { "height": 1397642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff0bf26f38104e192279f0dd6e77a29537f034347dc2c8a11aad6b6595d09254" } } ], "extra": [ 1, 184, 114, 24, 61, 231, 193, 162, 170, 229, 189, 58, 70, 105, 45, 89, 110, 37, 109, 116, 106, 148, 104, 14, 226, 250, 195, 212, 27, 79, 172, 133, 167, 2, 17, 0, 0, 0, 7, 93, 251, 190, 42, 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