Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a509d8a889128f604f80f47139ee65dfd5e9264d5f777926d35ae0221ed464c

Tx prefix hash: 31f77d494455c7c22c2e0810a496292379277e7ee5c9545d15f1ef87c6ac0a3e
Tx public key: 2c0b36e8ab46577de9382933a0c576d6bfb7b002b6f281414adb51d10b25a609
Timestamp: 1756043015 Timestamp [UCT]: 2025-08-24 13:43:35 Age [y:d:h:m:s]: 00:136:16:32:21
Block: 1353452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97693 RingCT/type: yes/0
Extra: 012c0b36e8ab46577de9382933a0c576d6bfb7b002b6f281414adb51d10b25a6090211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 182f06c9df20ab84724c4760077449efe5e971e41eff87e9e41f2baca995a54d 0.600000000000 1841427 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": 1353462, "vin": [ { "gen": { "height": 1353452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "182f06c9df20ab84724c4760077449efe5e971e41eff87e9e41f2baca995a54d" } } ], "extra": [ 1, 44, 11, 54, 232, 171, 70, 87, 125, 233, 56, 41, 51, 160, 197, 118, 214, 191, 183, 176, 2, 182, 242, 129, 65, 74, 219, 81, 209, 11, 37, 166, 9, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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