Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7edae3835588a7e5df0b3c4b614ba83e287e9510649f3c9e088654ea8a525c8e

Tx prefix hash: 924a5e793c84916550760c7ab126d78487560106fb1760a8a5f91830a72400f1
Tx public key: 0096afef794c206d71d30a3228f1eaa4a3684bed8d923af8b5bac8b5ff37b762
Timestamp: 1581312047 Timestamp [UCT]: 2020-02-10 05:20:47 Age [y:d:h:m:s]: 04:294:23:18:34
Block: 61756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102994 RingCT/type: yes/0
Extra: 010096afef794c206d71d30a3228f1eaa4a3684bed8d923af8b5bac8b5ff37b7620211000000018a2ee0d9000000000000000000

1 output(s) for total of 383.157694697000 dcy

stealth address amount amount idx
00: 890307fa514939a644241722587dee9f42faa013e3f12bfaa1958cfb2ef73172 383.157694697000 113887 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": 61766, "vin": [ { "gen": { "height": 61756 } } ], "vout": [ { "amount": 383157694697, "target": { "key": "890307fa514939a644241722587dee9f42faa013e3f12bfaa1958cfb2ef73172" } } ], "extra": [ 1, 0, 150, 175, 239, 121, 76, 32, 109, 113, 211, 10, 50, 40, 241, 234, 164, 163, 104, 75, 237, 141, 146, 58, 248, 181, 186, 200, 181, 255, 55, 183, 98, 2, 17, 0, 0, 0, 1, 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