Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c455409ce2d934dcabfb91d4d4260f1617d643246d0e63bf98d56815878c1bac

Tx prefix hash: e64c119129e539615a80dce06b0dad1750fee08a2a064019a1c1a83040043751
Tx public key: f04518e1f55b711ab86ef262ae9b5d57bd8cb3c9101c3b461d4c8843513fdf1f
Timestamp: 1581514921 Timestamp [UCT]: 2020-02-12 13:42:01 Age [y:d:h:m:s]: 04:331:10:19:04
Block: 63427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129079 RingCT/type: yes/0
Extra: 01f04518e1f55b711ab86ef262ae9b5d57bd8cb3c9101c3b461d4c8843513fdf1f021100000002c71d3ff9000000000000000000

1 output(s) for total of 378.303912175000 dcy

stealth address amount amount idx
00: 271eb247758b570be1a89d353a3bf36bfcdd5da2ba6016d338950b1cc34e03e2 378.303912175000 116977 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": 63437, "vin": [ { "gen": { "height": 63427 } } ], "vout": [ { "amount": 378303912175, "target": { "key": "271eb247758b570be1a89d353a3bf36bfcdd5da2ba6016d338950b1cc34e03e2" } } ], "extra": [ 1, 240, 69, 24, 225, 245, 91, 113, 26, 184, 110, 242, 98, 174, 155, 93, 87, 189, 140, 179, 201, 16, 28, 59, 70, 29, 76, 136, 67, 81, 63, 223, 31, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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