Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ff8a845a4b33dd40a60fd3cce532c3e3eef2899bfb0f8c4b97cc50630d94fa

Tx prefix hash: 46718438e5244ab7fe5f023d4c3462ee9f9d0eb5361f9a93cb62a74cd1dd15c6
Tx public key: 6654891726b5866fa4af15859263fa1c74a24a1dca83b4fad541be4721af0bd3
Timestamp: 1581642098 Timestamp [UCT]: 2020-02-14 01:01:38 Age [y:d:h:m:s]: 04:316:04:39:19
Block: 64572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118097 RingCT/type: yes/0
Extra: 016654891726b5866fa4af15859263fa1c74a24a1dca83b4fad541be4721af0bd3021100000002724f989b000000000000000000

1 output(s) for total of 375.049459126000 dcy

stealth address amount amount idx
00: fd6c42b82e56c19389c9e3758561ad11d472995c3b93ff4f984c813fba9721e8 375.049459126000 119081 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": 64582, "vin": [ { "gen": { "height": 64572 } } ], "vout": [ { "amount": 375049459126, "target": { "key": "fd6c42b82e56c19389c9e3758561ad11d472995c3b93ff4f984c813fba9721e8" } } ], "extra": [ 1, 102, 84, 137, 23, 38, 181, 134, 111, 164, 175, 21, 133, 146, 99, 250, 28, 116, 162, 74, 29, 202, 131, 180, 250, 213, 65, 190, 71, 33, 175, 11, 211, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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