Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79127227a17f33270c4de3549ba99e629705993c316e759f97dc41c3a28cbd81

Tx prefix hash: b453fdef36f551d482abd382f36ec9a8d1ffafdaf5b78b1066f5134551810b67
Tx public key: 993a188732afd89349440fd3702f7e7b48ec253f5b7697a75a97325b4c5e5ae5
Timestamp: 1726411183 Timestamp [UCT]: 2024-09-15 14:39:43 Age [y:d:h:m:s]: 00:221:02:40:02
Block: 1110711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157869 RingCT/type: yes/0
Extra: 01993a188732afd89349440fd3702f7e7b48ec253f5b7697a75a97325b4c5e5ae502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfbefb7bf57afd31c2a27679ac1587474a6c391fa3d232c69da9bfc4240d5658 0.600000000000 1589410 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": 1110721, "vin": [ { "gen": { "height": 1110711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfbefb7bf57afd31c2a27679ac1587474a6c391fa3d232c69da9bfc4240d5658" } } ], "extra": [ 1, 153, 58, 24, 135, 50, 175, 216, 147, 73, 68, 15, 211, 112, 47, 126, 123, 72, 236, 37, 63, 91, 118, 151, 167, 90, 151, 50, 91, 76, 94, 90, 229, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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