Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccd363a2f8bfa3e5e9bb61e602e59b4af25807dd8c74d6f6518b9b362e883b69

Tx prefix hash: 191f13ccbdf3f588b65f1f08362dd73b28bb1b55dc6c1264bf57606966ad4920
Tx public key: cf7adfde06bdfcb6c470136511ef9f52291a186f0d3ce610484384a969009c10
Timestamp: 1707675084 Timestamp [UCT]: 2024-02-11 18:11:24 Age [y:d:h:m:s]: 01:295:21:16:30
Block: 955367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470287 RingCT/type: yes/0
Extra: 01cf7adfde06bdfcb6c470136511ef9f52291a186f0d3ce610484384a969009c100211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbe0f81a4c05924a43cb35d14dbf6374a1594ba6ff268a56623b5a3ffe81b9e4 0.600000000000 1414655 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": 955377, "vin": [ { "gen": { "height": 955367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbe0f81a4c05924a43cb35d14dbf6374a1594ba6ff268a56623b5a3ffe81b9e4" } } ], "extra": [ 1, 207, 122, 223, 222, 6, 189, 252, 182, 196, 112, 19, 101, 17, 239, 159, 82, 41, 26, 24, 111, 13, 60, 230, 16, 72, 67, 132, 169, 105, 0, 156, 16, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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