Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff1d7a68c87daba6e6aa82c2f82d61fa05ca15ce3cdbe1f328d2979a1f714719

Tx prefix hash: 55879cd9834f1758fb78a9524830536d1b9b45715e45f4e9c7aceae6d2e1647f
Tx public key: ef76e32aae8ace3a35154a76845b130d357fe4cb79f914a3f2d2d51576aad27a
Timestamp: 1748713987 Timestamp [UCT]: 2025-05-31 17:53:07 Age [y:d:h:m:s]: 00:240:10:33:31
Block: 1295066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169442 RingCT/type: yes/0
Extra: 01ef76e32aae8ace3a35154a76845b130d357fe4cb79f914a3f2d2d51576aad27a02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31b80837887a501f18321fa941445f4e2f2b8f3ca7ca7b4d17d08417cfc432d2 0.600000000000 1782567 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": 1295076, "vin": [ { "gen": { "height": 1295066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b80837887a501f18321fa941445f4e2f2b8f3ca7ca7b4d17d08417cfc432d2" } } ], "extra": [ 1, 239, 118, 227, 42, 174, 138, 206, 58, 53, 21, 74, 118, 132, 91, 19, 13, 53, 127, 228, 203, 121, 249, 20, 163, 242, 210, 213, 21, 118, 170, 210, 122, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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