Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f548e6a60d39ce5e8faf2aa0c939354dfd7463a01f2193cb9f9016213a395216

Tx prefix hash: e81dc7f13b1a6b53cd8fbd8a091cc207be76aec5b8a6e6e6a9f1abd1ed65b1ee
Tx public key: 07b64fc5f898a6a942ff0e0ad27b7fbd27d4e59d5ee586686ea31c42a7406b2d
Timestamp: 1736133071 Timestamp [UCT]: 2025-01-06 03:11:11 Age [y:d:h:m:s]: 00:111:09:56:53
Block: 1191177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79427 RingCT/type: yes/0
Extra: 0107b64fc5f898a6a942ff0e0ad27b7fbd27d4e59d5ee586686ea31c42a7406b2d0211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58ac6ded3470d8c8defbcfe7ca505a72c16edb249e9755d71c4837f439920a00 0.600000000000 1677700 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": 1191187, "vin": [ { "gen": { "height": 1191177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58ac6ded3470d8c8defbcfe7ca505a72c16edb249e9755d71c4837f439920a00" } } ], "extra": [ 1, 7, 182, 79, 197, 248, 152, 166, 169, 66, 255, 14, 10, 210, 123, 127, 189, 39, 212, 229, 157, 94, 229, 134, 104, 110, 163, 28, 66, 167, 64, 107, 45, 2, 17, 0, 0, 0, 21, 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