Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79ff6ecb9052172b44786907da450b2580f9efd8ffa00408fee54c9c0c31dc43

Tx prefix hash: 6001abce2413b636aeadca42ed09617c1b8a51e9469baf882cf07f0905108495
Tx public key: b03efd6e1477e5f906bfce9f8bee8b25dc55a4c97acefdf890336f83462a2b82
Timestamp: 1733903530 Timestamp [UCT]: 2024-12-11 07:52:10 Age [y:d:h:m:s]: 00:102:00:51:34
Block: 1172727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72706 RingCT/type: yes/0
Extra: 01b03efd6e1477e5f906bfce9f8bee8b25dc55a4c97acefdf890336f83462a2b8202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fafd67b39ec0b715816e0b2430f0ca704151f38309c0c33d079efd9ce0ffbec 0.600000000000 1658656 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": 1172737, "vin": [ { "gen": { "height": 1172727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fafd67b39ec0b715816e0b2430f0ca704151f38309c0c33d079efd9ce0ffbec" } } ], "extra": [ 1, 176, 62, 253, 110, 20, 119, 229, 249, 6, 191, 206, 159, 139, 238, 139, 37, 220, 85, 164, 201, 122, 206, 253, 248, 144, 51, 111, 131, 70, 42, 43, 130, 2, 17, 0, 0, 0, 10, 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