Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ec18bd6a90489a77c50e84df89ef72b077b4b4b830b7c270e3f3cc46f7d333a

Tx prefix hash: 7115f78d07f3ced82b31978c2adc28b08480e1cc00aff16e161c7e3cda3595d3
Tx public key: 16eb56251c423e31190cfbb25258c4eb2fc983c331a24b0a5fc7e601c224543f
Timestamp: 1648518443 Timestamp [UCT]: 2022-03-29 01:47:23 Age [y:d:h:m:s]: 02:224:22:49:43
Block: 468601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680285 RingCT/type: yes/0
Extra: 0116eb56251c423e31190cfbb25258c4eb2fc983c331a24b0a5fc7e601c224543f0211000000184a0f5013000000000000000000

1 output(s) for total of 17.193336678000 dcy

stealth address amount amount idx
00: 097fa4524955a737e38149e7a59cb03675ea1b2956fa201b795c609de8fce33f 17.193336678000 887349 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": 468611, "vin": [ { "gen": { "height": 468601 } } ], "vout": [ { "amount": 17193336678, "target": { "key": "097fa4524955a737e38149e7a59cb03675ea1b2956fa201b795c609de8fce33f" } } ], "extra": [ 1, 22, 235, 86, 37, 28, 66, 62, 49, 25, 12, 251, 178, 82, 88, 196, 235, 47, 201, 131, 195, 49, 162, 75, 10, 95, 199, 230, 1, 194, 36, 84, 63, 2, 17, 0, 0, 0, 24, 74, 15, 80, 19, 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