Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c8e90f973dd93c3367e0f38581d15e390eae0aa1fc1fad58c57eb12857f044b

Tx prefix hash: f4e736988e22084cced7685682ec830e7e7b6ad225e9c95b1dbbc83d040a0d3b
Tx public key: 89c827aafcc4a58244751871514c4127624aa669405966606207b4e06ac9b0da
Timestamp: 1735142656 Timestamp [UCT]: 2024-12-25 16:04:16 Age [y:d:h:m:s]: 00:096:04:34:11
Block: 1182978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68530 RingCT/type: yes/0
Extra: 0189c827aafcc4a58244751871514c4127624aa669405966606207b4e06ac9b0da0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cfb9382e967390c9f37e2658206958f4d494dcaa493ef5c12d96e9dbdd5f01b 0.600000000000 1669417 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": 1182988, "vin": [ { "gen": { "height": 1182978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cfb9382e967390c9f37e2658206958f4d494dcaa493ef5c12d96e9dbdd5f01b" } } ], "extra": [ 1, 137, 200, 39, 170, 252, 196, 165, 130, 68, 117, 24, 113, 81, 76, 65, 39, 98, 74, 166, 105, 64, 89, 102, 96, 98, 7, 180, 224, 106, 201, 176, 218, 2, 17, 0, 0, 0, 2, 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