Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47a2500bf47ef65a451c852a6a3c78194456bae18ccb59653b847416b99cdc72

Tx prefix hash: 11d653384f48f660584d2771d206d3d90fdb57784e7ce2b654c684649881a2e6
Tx public key: 1172b2b9866e0d76c5327a87d2bbe399350e2678806284ac7980f7ae2129a59c
Timestamp: 1701582910 Timestamp [UCT]: 2023-12-03 05:55:10 Age [y:d:h:m:s]: 01:082:10:05:14
Block: 904861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320018 RingCT/type: yes/0
Extra: 011172b2b9866e0d76c5327a87d2bbe399350e2678806284ac7980f7ae2129a59c02110000000346113aa8000000000000000000

1 output(s) for total of 0.616339295000 dcy

stealth address amount amount idx
00: a076725a0d284e6280cae9d3c58d1db73697ea06e2f4dd8c9b7f740e7738e62f 0.616339295000 1361642 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": 904871, "vin": [ { "gen": { "height": 904861 } } ], "vout": [ { "amount": 616339295, "target": { "key": "a076725a0d284e6280cae9d3c58d1db73697ea06e2f4dd8c9b7f740e7738e62f" } } ], "extra": [ 1, 17, 114, 178, 185, 134, 110, 13, 118, 197, 50, 122, 135, 210, 187, 227, 153, 53, 14, 38, 120, 128, 98, 132, 172, 121, 128, 247, 174, 33, 41, 165, 156, 2, 17, 0, 0, 0, 3, 70, 17, 58, 168, 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