Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2e639d427e5aacdc1d77fd819312785b0dbc57f3136b208a953d2dc3d58f1f

Tx prefix hash: b1338736a3151c32785b8b9666177ef6495f6cdb44ed2d24efe62cbf0bb7e82b
Tx public key: 486cdef42f06ede7aafa28add2c9a183606c82e37e3ef64db741c148612b5bd5
Timestamp: 1715678986 Timestamp [UCT]: 2024-05-14 09:29:46 Age [y:d:h:m:s]: 00:286:10:58:33
Block: 1021738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204719 RingCT/type: yes/0
Extra: 01486cdef42f06ede7aafa28add2c9a183606c82e37e3ef64db741c148612b5bd502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c0e334504e5104f6eca192511fe15015560253bfd20eb62706f0d3a954c184 0.600000000000 1486139 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": 1021748, "vin": [ { "gen": { "height": 1021738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c0e334504e5104f6eca192511fe15015560253bfd20eb62706f0d3a954c184" } } ], "extra": [ 1, 72, 108, 222, 244, 47, 6, 237, 231, 170, 250, 40, 173, 210, 201, 161, 131, 96, 108, 130, 227, 126, 62, 246, 77, 183, 65, 193, 72, 97, 43, 91, 213, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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