Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b019e244aff5f1844e3f24c47ca4a968b5ec765fe81a4f49bfa4f88269014b3

Tx prefix hash: 361903a09d1f7e15e815e3a5bbabe929c5188d73e9eba6409175db80e4e65381
Tx public key: cc4ed47d39c7f11c84c4ff5497aaea22dc92e1cac2dcd0ec9ed5539832e0d37b
Timestamp: 1703808686 Timestamp [UCT]: 2023-12-29 00:11:26 Age [y:d:h:m:s]: 01:340:04:14:43
Block: 923323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501986 RingCT/type: yes/0
Extra: 01cc4ed47d39c7f11c84c4ff5497aaea22dc92e1cac2dcd0ec9ed5539832e0d37b021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b769472c74c15ec8f0ea42b034a4e628904f4514c30ad149b48a8dbdae23e64 0.600000000000 1381053 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": 923333, "vin": [ { "gen": { "height": 923323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b769472c74c15ec8f0ea42b034a4e628904f4514c30ad149b48a8dbdae23e64" } } ], "extra": [ 1, 204, 78, 212, 125, 57, 199, 241, 28, 132, 196, 255, 84, 151, 170, 234, 34, 220, 146, 225, 202, 194, 220, 208, 236, 158, 213, 83, 152, 50, 224, 211, 123, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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