Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966c48c2d9e5a80f3812e2df8b14d0e82fa0b6cd0b31fc6af2e755a599468142

Tx prefix hash: 463d1e71bb221bbf3d4930e475d1ab865b4cb8081ac9f786c25f428a53f8319e
Tx public key: a6e23480d59c4d38b5d8540283cb7bec7bd7b42dc6fefbc6a62d232728173286
Timestamp: 1578258000 Timestamp [UCT]: 2020-01-05 21:00:00 Age [y:d:h:m:s]: 04:358:17:52:07
Block: 39463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145606 RingCT/type: yes/0
Extra: 01a6e23480d59c4d38b5d8540283cb7bec7bd7b42dc6fefbc6a62d232728173286021100000029dcee4b4d000000000000000000

1 output(s) for total of 454.196253488000 dcy

stealth address amount amount idx
00: f0c45d27a7eebdf28961d23ecdce5d6a7050778ef4c9c4ecc8df8a91418050e0 454.196253488000 68115 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": 39473, "vin": [ { "gen": { "height": 39463 } } ], "vout": [ { "amount": 454196253488, "target": { "key": "f0c45d27a7eebdf28961d23ecdce5d6a7050778ef4c9c4ecc8df8a91418050e0" } } ], "extra": [ 1, 166, 226, 52, 128, 213, 156, 77, 56, 181, 216, 84, 2, 131, 203, 123, 236, 123, 215, 180, 45, 198, 254, 251, 198, 166, 45, 35, 39, 40, 23, 50, 134, 2, 17, 0, 0, 0, 41, 220, 238, 75, 77, 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