Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b53c9ef8cb3bf01d6e518ea45e7496af707c50fab682c16ee5efec0c2f34091

Tx prefix hash: db232ec79f8e339fc819dd0e4c49970b985f1fac3d434b82a93da8011c67e275
Tx public key: 2dc81ccebc4b89918cad978e361f6ba8971ad5a6f665ff55c7dfc7ca4bb3371d
Timestamp: 1705749007 Timestamp [UCT]: 2024-01-20 11:10:07 Age [y:d:h:m:s]: 01:074:19:30:53
Block: 939380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314571 RingCT/type: yes/0
Extra: 012dc81ccebc4b89918cad978e361f6ba8971ad5a6f665ff55c7dfc7ca4bb3371d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4162b5a616c8e2cf262d5f1303ad4872d53053a95817d4bf64fbb2b2acb2f93 0.600000000000 1397484 of 15

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": 939390, "vin": [ { "gen": { "height": 939380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4162b5a616c8e2cf262d5f1303ad4872d53053a95817d4bf64fbb2b2acb2f93" } } ], "extra": [ 1, 45, 200, 28, 206, 188, 75, 137, 145, 140, 173, 151, 142, 54, 31, 107, 168, 151, 26, 213, 166, 246, 101, 255, 85, 199, 223, 199, 202, 75, 179, 55, 29, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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