Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc659b19269b125acf484ea87f03ac55fd4fa57a7a331fb610490f93d7e0f546

Tx prefix hash: ed5415aba258821fc2d83aad1d50bdd98883e07c4944b5e6df80f2dc9d250e6f
Tx public key: 930317265754d2543b32014f70df7908955f44f0b975434124bea9ecf7f2c1e0
Timestamp: 1717569034 Timestamp [UCT]: 2024-06-05 06:30:34 Age [y:d:h:m:s]: 00:308:14:01:45
Block: 1037410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220523 RingCT/type: yes/0
Extra: 01930317265754d2543b32014f70df7908955f44f0b975434124bea9ecf7f2c1e002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0074fc945fdf0b5eace1325bae7003dfe5d1b63b3717f52ab4fb9b9567361e5 0.600000000000 1505941 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": 1037420, "vin": [ { "gen": { "height": 1037410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0074fc945fdf0b5eace1325bae7003dfe5d1b63b3717f52ab4fb9b9567361e5" } } ], "extra": [ 1, 147, 3, 23, 38, 87, 84, 210, 84, 59, 50, 1, 79, 112, 223, 121, 8, 149, 95, 68, 240, 185, 117, 67, 65, 36, 190, 169, 236, 247, 242, 193, 224, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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