Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c06b998b1011057e0248ee9536a6c06b0601e5b0c6455a155e0eb8830ea6df01

Tx prefix hash: a20ac5e37fb479d16e1546d7daa7151d42386577225a508caa8910eb234851d3
Tx public key: 684c37da719a6a1c2939d83c706690eee071ccee409e65dff5eeb3879033c2ec
Timestamp: 1735128431 Timestamp [UCT]: 2024-12-25 12:07:11 Age [y:d:h:m:s]: 00:172:00:50:55
Block: 1182860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122682 RingCT/type: yes/0
Extra: 01684c37da719a6a1c2939d83c706690eee071ccee409e65dff5eeb3879033c2ec0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f7f1f0f328978b526e43a8ef0e557c2537f8fdcc21e6ac39214fad989317b3 0.600000000000 1669299 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": 1182870, "vin": [ { "gen": { "height": 1182860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f7f1f0f328978b526e43a8ef0e557c2537f8fdcc21e6ac39214fad989317b3" } } ], "extra": [ 1, 104, 76, 55, 218, 113, 154, 106, 28, 41, 57, 216, 60, 112, 102, 144, 238, 224, 113, 204, 238, 64, 158, 101, 223, 245, 238, 179, 135, 144, 51, 194, 236, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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