Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba9bbbf0801c86bb53bc6864ba218db89c5f5ddabd0c955e62f4c20821a55be0

Tx prefix hash: 4e7faf3e4306cb77f681b173104801375fa714c0f451aac5af75d1b84acae874
Tx public key: 7d70ccd39187f282f720c35e60ed17f840120321f9c6a5ce0c9190d2db139426
Timestamp: 1749714826 Timestamp [UCT]: 2025-06-12 07:53:46 Age [y:d:h:m:s]: 00:150:23:43:53
Block: 1303314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105623 RingCT/type: yes/0
Extra: 017d70ccd39187f282f720c35e60ed17f840120321f9c6a5ce0c9190d2db139426021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c752fd200006d7d2e0310f9b8489854c18249d2f5e7875174e62f084a6039a0 0.600000000000 1790893 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": 1303324, "vin": [ { "gen": { "height": 1303314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c752fd200006d7d2e0310f9b8489854c18249d2f5e7875174e62f084a6039a0" } } ], "extra": [ 1, 125, 112, 204, 211, 145, 135, 242, 130, 247, 32, 195, 94, 96, 237, 23, 248, 64, 18, 3, 33, 249, 198, 165, 206, 12, 145, 144, 210, 219, 19, 148, 38, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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