Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071c7dfd2a79ac8bc91a35a59dd5429ad0ad4aa5268d45db25dc0ce808d3e132

Tx prefix hash: f3da34a0d8635d3ed066fa3f9db6a47f439f0e3f4a3a69f6890d6ae2c2fb2f3d
Tx public key: 99c826c38693537504c40336ef45a9813dec40cc751301a0e41a6f708cd24586
Timestamp: 1763308268 Timestamp [UCT]: 2025-11-16 15:51:08 Age [y:d:h:m:s]: 00:037:10:04:58
Block: 1413471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26791 RingCT/type: yes/0
Extra: 0199c826c38693537504c40336ef45a9813dec40cc751301a0e41a6f708cd2458602110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79934ceef832b8027a984cbae6af104f888c7f1b3149c6b07caf0c79d2c49c41 0.600000000000 1901950 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": 1413481, "vin": [ { "gen": { "height": 1413471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79934ceef832b8027a984cbae6af104f888c7f1b3149c6b07caf0c79d2c49c41" } } ], "extra": [ 1, 153, 200, 38, 195, 134, 147, 83, 117, 4, 196, 3, 54, 239, 69, 169, 129, 61, 236, 64, 204, 117, 19, 1, 160, 228, 26, 111, 112, 140, 210, 69, 134, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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