Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e7c34e383e9141afc0df49b40851067d482d27b691f59b1b5cb4af9c1abf532

Tx prefix hash: 8f653f8557b1dfaffa31096d371aa1c0ee459d9bfb5f775d9586b7f91e570717
Tx public key: 675336026cfa3a16918c48dc765aa6dc83606b02266bd1094876116fb7540dfd
Timestamp: 1711072672 Timestamp [UCT]: 2024-03-22 01:57:52 Age [y:d:h:m:s]: 00:277:22:59:49
Block: 983564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198968 RingCT/type: yes/0
Extra: 01675336026cfa3a16918c48dc765aa6dc83606b02266bd1094876116fb7540dfd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 865ff22e90278fb2b0170c0e6486a7a7f2313b335e9e715b37db38d63237d04e 0.600000000000 1443705 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": 983574, "vin": [ { "gen": { "height": 983564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "865ff22e90278fb2b0170c0e6486a7a7f2313b335e9e715b37db38d63237d04e" } } ], "extra": [ 1, 103, 83, 54, 2, 108, 250, 58, 22, 145, 140, 72, 220, 118, 90, 166, 220, 131, 96, 107, 2, 38, 107, 209, 9, 72, 118, 17, 111, 183, 84, 13, 253, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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