Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed026e10bea82b4b88ec2f1df392cdb04a5c7534f838189e65f5f5dee1fd100

Tx prefix hash: db16e1d19106408b314979b2be9f854c9da818eba419701f6c641978b5e5e0c3
Tx public key: fa0ee5472e9e27e453abea415f90556ded4f7d8d5cb32665c0bc835c734de0d9
Timestamp: 1698676643 Timestamp [UCT]: 2023-10-30 14:37:23 Age [y:d:h:m:s]: 01:093:08:01:31
Block: 880995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327657 RingCT/type: yes/0
Extra: 01fa0ee5472e9e27e453abea415f90556ded4f7d8d5cb32665c0bc835c734de0d902110000000233af99f4000000000000000000

1 output(s) for total of 0.739431347000 dcy

stealth address amount amount idx
00: a3902e716cfa02f98ce14de9fb853118ca4340565f774b3c9c8223b19f28cfb1 0.739431347000 1336565 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": 881005, "vin": [ { "gen": { "height": 880995 } } ], "vout": [ { "amount": 739431347, "target": { "key": "a3902e716cfa02f98ce14de9fb853118ca4340565f774b3c9c8223b19f28cfb1" } } ], "extra": [ 1, 250, 14, 229, 71, 46, 158, 39, 228, 83, 171, 234, 65, 95, 144, 85, 109, 237, 79, 125, 141, 92, 179, 38, 101, 192, 188, 131, 92, 115, 77, 224, 217, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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