Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1aeaf47f54eba05a570d3984a961b9c1ae24f497380eb538ff436ab94fe225f

Tx prefix hash: 08453115515cffd1bbc16f26644c0b993220ec629958bd504ca6e1b64609c8d9
Tx public key: 7fa88c6f561a14b6a858ffd7962f67c4df6ab9dd72fdff786186aab0b0f5fce8
Timestamp: 1718182889 Timestamp [UCT]: 2024-06-12 09:01:29 Age [y:d:h:m:s]: 00:299:01:48:01
Block: 1042498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213711 RingCT/type: yes/0
Extra: 017fa88c6f561a14b6a858ffd7962f67c4df6ab9dd72fdff786186aab0b0f5fce80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4817c3de275df65bd636bd17cd15da37d633e9f231766e249a98b1284819aea9 0.600000000000 1511431 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": 1042508, "vin": [ { "gen": { "height": 1042498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4817c3de275df65bd636bd17cd15da37d633e9f231766e249a98b1284819aea9" } } ], "extra": [ 1, 127, 168, 140, 111, 86, 26, 20, 182, 168, 88, 255, 215, 150, 47, 103, 196, 223, 106, 185, 221, 114, 253, 255, 120, 97, 134, 170, 176, 176, 245, 252, 232, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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