Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a656f25ca8da7307f3c5d44720e19d6719fa27556aaf3d6f6ee2bd2040d796

Tx prefix hash: 745b0263371d6e28c7f165b50961e982da3b5f9d4568e2237c5307f08ef6d07a
Tx public key: 00211c0b58dec226e9bd0a40cd48dd215081dadd22b477a726194ecf65f54b23
Timestamp: 1574554834 Timestamp [UCT]: 2019-11-24 00:20:34 Age [y:d:h:m:s]: 05:045:22:38:56
Block: 16031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1175723 RingCT/type: yes/0
Extra: 0100211c0b58dec226e9bd0a40cd48dd215081dadd22b477a726194ecf65f54b2302110000002e354bbe3b000000000000000000

1 output(s) for total of 543.104654592000 dcy

stealth address amount amount idx
00: 19caaafcbcf652d9f3c941cdb325f4d46b0e41ce91651b424e8dbda3c74c7142 543.104654592000 22092 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": 16041, "vin": [ { "gen": { "height": 16031 } } ], "vout": [ { "amount": 543104654592, "target": { "key": "19caaafcbcf652d9f3c941cdb325f4d46b0e41ce91651b424e8dbda3c74c7142" } } ], "extra": [ 1, 0, 33, 28, 11, 88, 222, 194, 38, 233, 189, 10, 64, 205, 72, 221, 33, 80, 129, 218, 221, 34, 180, 119, 167, 38, 25, 78, 207, 101, 245, 75, 35, 2, 17, 0, 0, 0, 46, 53, 75, 190, 59, 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