Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e019a30069576d101110c327f3ced6f5ad502216d7e37a2ba6b74f83e4eff32

Tx prefix hash: 0c5ba12954ff83600235d443530f40b52650d88ee6d9c0a0e5ec94150f42939c
Tx public key: ff3d57eb019f0d8f60d2d8d08f3724b58d82b702aad168a34281f85c19d133f9
Timestamp: 1740903726 Timestamp [UCT]: 2025-03-02 08:22:06 Age [y:d:h:m:s]: 00:259:15:36:29
Block: 1230395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183323 RingCT/type: yes/0
Extra: 01ff3d57eb019f0d8f60d2d8d08f3724b58d82b702aad168a34281f85c19d133f9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e52a5fdf980028d069a1ba2cc625225681a1afbb4b2ce16b853682fadf1afea4 0.600000000000 1717292 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": 1230405, "vin": [ { "gen": { "height": 1230395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e52a5fdf980028d069a1ba2cc625225681a1afbb4b2ce16b853682fadf1afea4" } } ], "extra": [ 1, 255, 61, 87, 235, 1, 159, 13, 143, 96, 210, 216, 208, 143, 55, 36, 181, 141, 130, 183, 2, 170, 209, 104, 163, 66, 129, 248, 92, 25, 209, 51, 249, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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