Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81365c7a462d946dc331cc1ee0b3037e8b996e7288563e9377c4241c00378253

Tx prefix hash: c396412f9749c2201edd53c68dcc6d714aca56350b35f4b68f412179b725ce9b
Tx public key: 661cf6e850931f8658b09d26d437b6238302410df2013eaf0077c8085bafaab1
Timestamp: 1580570630 Timestamp [UCT]: 2020-02-01 15:23:50 Age [y:d:h:m:s]: 05:037:21:35:33
Block: 56682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178869 RingCT/type: yes/0
Extra: 01661cf6e850931f8658b09d26d437b6238302410df2013eaf0077c8085bafaab1021100000005dcee4b4d000000000000000000

1 output(s) for total of 398.281218718000 dcy

stealth address amount amount idx
00: d8cfebaddfc0b1c8a7b4e0f01b6b8509460c5dbd79b30b8cff7ff3487956ffaa 398.281218718000 104473 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": 56692, "vin": [ { "gen": { "height": 56682 } } ], "vout": [ { "amount": 398281218718, "target": { "key": "d8cfebaddfc0b1c8a7b4e0f01b6b8509460c5dbd79b30b8cff7ff3487956ffaa" } } ], "extra": [ 1, 102, 28, 246, 232, 80, 147, 31, 134, 88, 176, 157, 38, 212, 55, 182, 35, 131, 2, 65, 13, 242, 1, 62, 175, 0, 119, 200, 8, 91, 175, 170, 177, 2, 17, 0, 0, 0, 5, 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