Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89b99d4eed40c67234c09e2fdc37562df08a98a04434176b4fc4ee00deeea2be

Tx prefix hash: d8c86a092f9c87ac3da4efe84d4f1acc74244ef40b633bd9f2a076978b6cde8c
Tx public key: 1662966cde87e1a8bc38af1bf6ccc4ae9502df5558aa207272b30529d2333911
Timestamp: 1582383326 Timestamp [UCT]: 2020-02-22 14:55:26 Age [y:d:h:m:s]: 04:279:21:30:06
Block: 70234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092598 RingCT/type: yes/0
Extra: 011662966cde87e1a8bc38af1bf6ccc4ae9502df5558aa207272b30529d2333911021100000001026b59f3000000000000000000

1 output(s) for total of 359.208312310000 dcy

stealth address amount amount idx
00: 59b0c70ddf79f7e8410ac1cb91d245459ab3eb477588364912f88670370e48e4 359.208312310000 129701 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": 70244, "vin": [ { "gen": { "height": 70234 } } ], "vout": [ { "amount": 359208312310, "target": { "key": "59b0c70ddf79f7e8410ac1cb91d245459ab3eb477588364912f88670370e48e4" } } ], "extra": [ 1, 22, 98, 150, 108, 222, 135, 225, 168, 188, 56, 175, 27, 246, 204, 196, 174, 149, 2, 223, 85, 88, 170, 32, 114, 114, 179, 5, 41, 210, 51, 57, 17, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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