Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3bb5ebfa1349f0b852f1037b4c76caf4f49bb563f7114c7837de22ececdfeb4

Tx prefix hash: 65ce43d1f1f7e59d7bde585a8062a48b7b31e90245b0ca865cd8046cca85b3e2
Tx public key: b0171b5a12e8f06de31eacb12f056919b47ac4fd7257553ed90177c0222c29e9
Timestamp: 1710354311 Timestamp [UCT]: 2024-03-13 18:25:11 Age [y:d:h:m:s]: 01:039:23:56:59
Block: 977604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289568 RingCT/type: yes/0
Extra: 01b0171b5a12e8f06de31eacb12f056919b47ac4fd7257553ed90177c0222c29e90211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770fd29be9a8cca62b13f268b96c0c1692cfd5b74732d5f5aa9084adf48ae7eb 0.600000000000 1437607 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": 977614, "vin": [ { "gen": { "height": 977604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770fd29be9a8cca62b13f268b96c0c1692cfd5b74732d5f5aa9084adf48ae7eb" } } ], "extra": [ 1, 176, 23, 27, 90, 18, 232, 240, 109, 227, 30, 172, 177, 47, 5, 105, 25, 180, 122, 196, 253, 114, 87, 85, 62, 217, 1, 119, 192, 34, 44, 41, 233, 2, 17, 0, 0, 0, 5, 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