Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b37de95651d1bab6c44ede2b1cdbc06a47cbb2d815a80d51398cd3eef4d8761

Tx prefix hash: af9a6f8b3098ee9256d40608f35aff1ae6d38fdcdaee650222dff3b5790aaa54
Tx public key: 066dae60d2e2a67761d70532c88921f60facb197f9ccbbf844d7915ed95ffc43
Timestamp: 1591544239 Timestamp [UCT]: 2020-06-07 15:37:19 Age [y:d:h:m:s]: 04:262:01:34:16
Block: 106045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119592 RingCT/type: yes/0
Extra: 01066dae60d2e2a67761d70532c88921f60facb197f9ccbbf844d7915ed95ffc4302110000000425a1e897000000000000000000

1 output(s) for total of 273.293717031000 dcy

stealth address amount amount idx
00: 4efc1060d26e8022a4f098ec26efa69a9eeb2ea5052557437e6005149d516cba 273.293717031000 185284 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": 106055, "vin": [ { "gen": { "height": 106045 } } ], "vout": [ { "amount": 273293717031, "target": { "key": "4efc1060d26e8022a4f098ec26efa69a9eeb2ea5052557437e6005149d516cba" } } ], "extra": [ 1, 6, 109, 174, 96, 210, 226, 166, 119, 97, 215, 5, 50, 200, 137, 33, 246, 15, 172, 177, 151, 249, 204, 187, 248, 68, 215, 145, 94, 217, 95, 252, 67, 2, 17, 0, 0, 0, 4, 37, 161, 232, 151, 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