Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018b1c364fc0ccb2f0d4b1d9be06497fb8ab71baa994e86b5724d1e09693f7bb

Tx prefix hash: e9e664be4a98467fef173587e73b3f3473ab77a4e86321772f8fff0bca7172a7
Tx public key: ef2fa7baeb38e3fc0bec533286c0a0985f4a78c3e71f840c7b88ae1bac1042b8
Timestamp: 1581944195 Timestamp [UCT]: 2020-02-17 12:56:35 Age [y:d:h:m:s]: 04:275:18:40:31
Block: 66601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089642 RingCT/type: yes/0
Extra: 01ef2fa7baeb38e3fc0bec533286c0a0985f4a78c3e71f840c7b88ae1bac1042b80211000000088a2ee0d9000000000000000000

1 output(s) for total of 369.253013468000 dcy

stealth address amount amount idx
00: c0d9764d505df3fb5b7079b054108979d1c37131061396d701c5b620bd02db5d 369.253013468000 122726 of 0

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": 66611, "vin": [ { "gen": { "height": 66601 } } ], "vout": [ { "amount": 369253013468, "target": { "key": "c0d9764d505df3fb5b7079b054108979d1c37131061396d701c5b620bd02db5d" } } ], "extra": [ 1, 239, 47, 167, 186, 235, 56, 227, 252, 11, 236, 83, 50, 134, 192, 160, 152, 95, 74, 120, 195, 231, 31, 132, 12, 123, 136, 174, 27, 172, 16, 66, 184, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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