Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44ccaa22f509fa04414ef69e946cd7e5c1d337cf491b756884796c8c43333f2

Tx prefix hash: 5581a8a6ac55b193cae3fb0c10fb2231681856d415d527d5a1ac6ffa9356eec2
Tx public key: 90366d2d1378e76ab48ca909d31befc0fe5dd3e796a7e2d144fc826c3c917516
Timestamp: 1750092456 Timestamp [UCT]: 2025-06-16 16:47:36 Age [y:d:h:m:s]: 00:158:06:43:28
Block: 1306362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110918 RingCT/type: yes/0
Extra: 0190366d2d1378e76ab48ca909d31befc0fe5dd3e796a7e2d144fc826c3c9175160211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a46bb3328b58e64de929d31a4c053ab15d67ea62460314f9281e45e968a0d5f1 0.600000000000 1793967 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": 1306372, "vin": [ { "gen": { "height": 1306362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a46bb3328b58e64de929d31a4c053ab15d67ea62460314f9281e45e968a0d5f1" } } ], "extra": [ 1, 144, 54, 109, 45, 19, 120, 231, 106, 180, 140, 169, 9, 211, 27, 239, 192, 254, 93, 211, 231, 150, 167, 226, 209, 68, 252, 130, 108, 60, 145, 117, 22, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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