Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6738b1564a839547a0ad423c02961914715e4f7f4f5bff290c060aec366513

Tx prefix hash: f0af6d56994e3d8617b7486fc65e692dae68b1be5a4f1def79bfc7186174bc6c
Tx public key: fb1a1af7f360e5693d3eb606cea5981b96fa1b506b82430422d09ab65473f69d
Timestamp: 1702588442 Timestamp [UCT]: 2023-12-14 21:14:02 Age [y:d:h:m:s]: 01:334:16:30:28
Block: 913193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498070 RingCT/type: yes/0
Extra: 01fb1a1af7f360e5693d3eb606cea5981b96fa1b506b82430422d09ab65473f69d02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4c3da818b52ce4a2678e286addba7c39b9f60f485a3124b03e63d4e7047148d 0.600000000000 1370439 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": 913203, "vin": [ { "gen": { "height": 913193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4c3da818b52ce4a2678e286addba7c39b9f60f485a3124b03e63d4e7047148d" } } ], "extra": [ 1, 251, 26, 26, 247, 243, 96, 229, 105, 61, 62, 182, 6, 206, 165, 152, 27, 150, 250, 27, 80, 107, 130, 67, 4, 34, 208, 154, 182, 84, 115, 246, 157, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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