Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be1ddd30ffedf1102e590943a8cd8ecb5a22ed67e151dacab8caa09dd00433d

Tx prefix hash: d7b41e75fcdd7092b20a0760b0d0c0d962a93648c8ceaf2a757c3a66baa7be0f
Tx public key: d58d44fb4981ec0a6bed8ff523555bc87bcaa8bbfc9d3d72f0f17e588bb0df60
Timestamp: 1705682742 Timestamp [UCT]: 2024-01-19 16:45:42 Age [y:d:h:m:s]: 01:094:01:50:38
Block: 938829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328349 RingCT/type: yes/0
Extra: 01d58d44fb4981ec0a6bed8ff523555bc87bcaa8bbfc9d3d72f0f17e588bb0df6002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 473642f82da9e7ba4a21851657baad77493b771a5938aa999e8c3130d0147d98 0.600000000000 1396911 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": 938839, "vin": [ { "gen": { "height": 938829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "473642f82da9e7ba4a21851657baad77493b771a5938aa999e8c3130d0147d98" } } ], "extra": [ 1, 213, 141, 68, 251, 73, 129, 236, 10, 107, 237, 143, 245, 35, 85, 91, 200, 123, 202, 168, 187, 252, 157, 61, 114, 240, 241, 126, 88, 139, 176, 223, 96, 2, 17, 0, 0, 0, 6, 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