Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ff8b5e817301822e66b4e7578037304d7dbfc7f84fbe0cccda486364e8d20d

Tx prefix hash: ac7e65d5cec7ce5aca9359f018ff3bcd1478c83f45241ee839c68eeb8d9d0e2a
Tx public key: e52488832e7ba052b4fbc31fecde1329c21dec5a17fec4930f0e42e5ee71e50f
Timestamp: 1700833223 Timestamp [UCT]: 2023-11-24 13:40:23 Age [y:d:h:m:s]: 01:056:05:49:34
Block: 898658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301550 RingCT/type: yes/0
Extra: 01e52488832e7ba052b4fbc31fecde1329c21dec5a17fec4930f0e42e5ee71e50f021100000006faf35c9c000000000000000000

1 output(s) for total of 0.646208968000 dcy

stealth address amount amount idx
00: 4f5438ba57cfcb24f8125c74ee6852f7c38a0111fbfac99bdbb45295c9144e95 0.646208968000 1355087 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": 898668, "vin": [ { "gen": { "height": 898658 } } ], "vout": [ { "amount": 646208968, "target": { "key": "4f5438ba57cfcb24f8125c74ee6852f7c38a0111fbfac99bdbb45295c9144e95" } } ], "extra": [ 1, 229, 36, 136, 131, 46, 123, 160, 82, 180, 251, 195, 31, 236, 222, 19, 41, 194, 29, 236, 90, 23, 254, 196, 147, 15, 14, 66, 229, 238, 113, 229, 15, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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