Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e50f4f35904bb2a1637d4c344ac642c541d17030f003e68ce6d8771992dab8c

Tx prefix hash: 6b0442c4310999a7efe9032c4613d9e1d9a44052ceb6c42f0d77fa6ae7d52632
Tx public key: 72db39a2384b9d87f806e70414e87f7f609902ea7fd3a62fd74730198ca76ec4
Timestamp: 1736562411 Timestamp [UCT]: 2025-01-11 02:26:51 Age [y:d:h:m:s]: 00:116:05:44:17
Block: 1194720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82879 RingCT/type: yes/0
Extra: 0172db39a2384b9d87f806e70414e87f7f609902ea7fd3a62fd74730198ca76ec4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd7164dffc7e4cf9ec97e757b4326db5dcdc9248b29d50b5e3819e00d93689f2 0.600000000000 1681297 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": 1194730, "vin": [ { "gen": { "height": 1194720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd7164dffc7e4cf9ec97e757b4326db5dcdc9248b29d50b5e3819e00d93689f2" } } ], "extra": [ 1, 114, 219, 57, 162, 56, 75, 157, 135, 248, 6, 231, 4, 20, 232, 127, 127, 96, 153, 2, 234, 127, 211, 166, 47, 215, 71, 48, 25, 140, 167, 110, 196, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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