Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b30bafc40f0c7f4261541ce90d0815ad3d66da1a59154809864d569607b2d0

Tx prefix hash: 1e61cc6bd3b322a817da827655f43f8959d7b58fda6de64c61305413271a71bc
Tx public key: 3d84a7ba5b7c43be53f8f5adbe6937624cd69e9af19f32bf0f801f46df3ec743
Timestamp: 1761831788 Timestamp [UCT]: 2025-10-30 13:43:08 Age [y:d:h:m:s]: 00:021:03:59:01
Block: 1401241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15148 RingCT/type: yes/0
Extra: 013d84a7ba5b7c43be53f8f5adbe6937624cd69e9af19f32bf0f801f46df3ec7430211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b257ddbe716345a8c264d7157595c1540b199f8340436eb34b14df3efd9b39ca 0.600000000000 1889560 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": 1401251, "vin": [ { "gen": { "height": 1401241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b257ddbe716345a8c264d7157595c1540b199f8340436eb34b14df3efd9b39ca" } } ], "extra": [ 1, 61, 132, 167, 186, 91, 124, 67, 190, 83, 248, 245, 173, 190, 105, 55, 98, 76, 214, 158, 154, 241, 159, 50, 191, 15, 128, 31, 70, 223, 62, 199, 67, 2, 17, 0, 0, 0, 1, 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