Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1009aed5da0373d083071406156d97439fd52f10cb2cd3c23f6d2eca4d4d1335

Tx prefix hash: e3ea29355b4c73cde8cbc1c4f8c61886808c636061f5bbb6b6dc7a6eeaf45b32
Tx public key: 172816e6931b8e49497acb6004977249f684d231ddbe8c649f3ef8902a8e567c
Timestamp: 1714208904 Timestamp [UCT]: 2024-04-27 09:08:24 Age [y:d:h:m:s]: 01:221:18:00:44
Block: 1009539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417174 RingCT/type: yes/0
Extra: 01172816e6931b8e49497acb6004977249f684d231ddbe8c649f3ef8902a8e567c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c63f5ef76b5a2ed8d7f4cc621d12e0d891936e63aa2133c0f9df1bd2d6ead564 0.600000000000 1471243 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": 1009549, "vin": [ { "gen": { "height": 1009539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c63f5ef76b5a2ed8d7f4cc621d12e0d891936e63aa2133c0f9df1bd2d6ead564" } } ], "extra": [ 1, 23, 40, 22, 230, 147, 27, 142, 73, 73, 122, 203, 96, 4, 151, 114, 73, 246, 132, 210, 49, 221, 190, 140, 100, 159, 62, 248, 144, 42, 142, 86, 124, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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