Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4eb9898b64ebdcaee135f1d35bd77efcc67f322a97daebad9dff6dd85c62b1

Tx prefix hash: 7761e83015f7fe1c3fe64813d7e9b59a4723bf653ff37589e44f867b3cd33da7
Tx public key: 9e040e51ebe8c9d31129f02c822caae4f7138cb44e407f4516b7727defe0af30
Timestamp: 1716730762 Timestamp [UCT]: 2024-05-26 13:39:22 Age [y:d:h:m:s]: 00:334:15:58:38
Block: 1030461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239195 RingCT/type: yes/0
Extra: 019e040e51ebe8c9d31129f02c822caae4f7138cb44e407f4516b7727defe0af300211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60c0c2e5e5625316dcc79f93579ec4400ff72d935b026cd35aca39bdf227dd3b 0.600000000000 1498716 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": 1030471, "vin": [ { "gen": { "height": 1030461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60c0c2e5e5625316dcc79f93579ec4400ff72d935b026cd35aca39bdf227dd3b" } } ], "extra": [ 1, 158, 4, 14, 81, 235, 232, 201, 211, 17, 41, 240, 44, 130, 44, 170, 228, 247, 19, 140, 180, 78, 64, 127, 69, 22, 183, 114, 125, 239, 224, 175, 48, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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