Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dec25fe7d1e471f34696d65bfc19a9098b2806f2f831b8ee054cc03583615ee7

Tx prefix hash: 62dc0f22ee3c82bf6c8802b07741f03ad439a8af6fc2bdd5ee3f9051984c23e7
Tx public key: a60858fe8d3467c9253026bb6ed1f12fc8947261f0d70b99e296537214d04efb
Timestamp: 1710399882 Timestamp [UCT]: 2024-03-14 07:04:42 Age [y:d:h:m:s]: 01:024:04:08:01
Block: 977986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278238 RingCT/type: yes/0
Extra: 01a60858fe8d3467c9253026bb6ed1f12fc8947261f0d70b99e296537214d04efb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b151e41c6e4adf424a9f3859719a249e9e2d43ce11e3eef028fd91d0def5970e 0.600000000000 1437995 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": 977996, "vin": [ { "gen": { "height": 977986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b151e41c6e4adf424a9f3859719a249e9e2d43ce11e3eef028fd91d0def5970e" } } ], "extra": [ 1, 166, 8, 88, 254, 141, 52, 103, 201, 37, 48, 38, 187, 110, 209, 241, 47, 200, 148, 114, 97, 240, 215, 11, 153, 226, 150, 83, 114, 20, 208, 78, 251, 2, 17, 0, 0, 0, 4, 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