Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aae7d0aa022e4a04ce9db74c6de998464bc350000a5eae658987dd4d95184f3d

Tx prefix hash: c56acbf7f49301a605c142135d89e2546191e63ecbb7fe6cf0e035a1aea2504e
Tx public key: d1a7a83c2be391f7b13b75b0021de90d0afb4307904fa843d23afe083c71b2cc
Timestamp: 1707132516 Timestamp [UCT]: 2024-02-05 11:28:36 Age [y:d:h:m:s]: 01:100:00:24:14
Block: 950867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332567 RingCT/type: yes/0
Extra: 01d1a7a83c2be391f7b13b75b0021de90d0afb4307904fa843d23afe083c71b2cc0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49cb3e51f78392c18015985298517271d136e38f54623bd1c23a257a01a42766 0.600000000000 1409553 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": 950877, "vin": [ { "gen": { "height": 950867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49cb3e51f78392c18015985298517271d136e38f54623bd1c23a257a01a42766" } } ], "extra": [ 1, 209, 167, 168, 60, 43, 227, 145, 247, 177, 59, 117, 176, 2, 29, 233, 13, 10, 251, 67, 7, 144, 79, 168, 67, 210, 58, 254, 8, 60, 113, 178, 204, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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