Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c4619d3c430fc1cf251c11eaf8258c264ba7c4b510081d44992471f7344f0d0

Tx prefix hash: f4322e03889e86a36109daec0438cdd7ecab4e2a51dbce3aa3d50b04b33e62ac
Tx public key: d73267330629508baeab52f865ecd660408fc4fe8b6acef3b7a81260853d2868
Timestamp: 1584921372 Timestamp [UCT]: 2020-03-22 23:56:12 Age [y:d:h:m:s]: 04:321:07:40:34
Block: 86831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126375 RingCT/type: yes/0
Extra: 01d73267330629508baeab52f865ecd660408fc4fe8b6acef3b7a81260853d28680211000000164943cd9f000000000000000000

1 output(s) for total of 316.447113673000 dcy

stealth address amount amount idx
00: 2472966c1be52e3f9e6aa9bbaa10a1ec1aaf86a1ab244f827e93b354c9482624 316.447113673000 156653 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": 86841, "vin": [ { "gen": { "height": 86831 } } ], "vout": [ { "amount": 316447113673, "target": { "key": "2472966c1be52e3f9e6aa9bbaa10a1ec1aaf86a1ab244f827e93b354c9482624" } } ], "extra": [ 1, 215, 50, 103, 51, 6, 41, 80, 139, 174, 171, 82, 248, 101, 236, 214, 96, 64, 143, 196, 254, 139, 106, 206, 243, 183, 168, 18, 96, 133, 61, 40, 104, 2, 17, 0, 0, 0, 22, 73, 67, 205, 159, 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