Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 805f364ac5e991e84bb339304d4b5afbe57a17b6d9d9dd8cc81c6bccc900d601

Tx prefix hash: 8a25af280614114ec4ffdcc233c29b1c9bc8dd9f4215b173afec1967e8f02f7e
Tx public key: 207d29f0ca4bad44d2ba364d64d113709520cf3ed79c3873c7b075bb7bbd4c96
Timestamp: 1734626639 Timestamp [UCT]: 2024-12-19 16:43:59 Age [y:d:h:m:s]: 00:095:03:07:56
Block: 1178731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67738 RingCT/type: yes/0
Extra: 01207d29f0ca4bad44d2ba364d64d113709520cf3ed79c3873c7b075bb7bbd4c96021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9d563d96cf0367b3ac75f0d069de9efaabb9a4d28f0e6511bf0edf3d73ede7 0.600000000000 1665120 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": 1178741, "vin": [ { "gen": { "height": 1178731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9d563d96cf0367b3ac75f0d069de9efaabb9a4d28f0e6511bf0edf3d73ede7" } } ], "extra": [ 1, 32, 125, 41, 240, 202, 75, 173, 68, 210, 186, 54, 77, 100, 209, 19, 112, 149, 32, 207, 62, 215, 156, 56, 115, 199, 176, 117, 187, 123, 189, 76, 150, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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