Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 006e410201964cb6d0e4b7a3e1d665a66e90a76f99c7c40ad29d84265a3fbc92

Tx prefix hash: dc05dbcbcb2b6006e8ae8d65177a87595c9e0e555870dd53237f2dbe3c1a1898
Tx public key: f3d4b57e29dcc0f28955f72e86a849b17afd5c3a5f42dbd77ad4dc42359b35b0
Timestamp: 1711300033 Timestamp [UCT]: 2024-03-24 17:07:13 Age [y:d:h:m:s]: 01:228:17:29:41
Block: 985449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422142 RingCT/type: yes/0
Extra: 01f3d4b57e29dcc0f28955f72e86a849b17afd5c3a5f42dbd77ad4dc42359b35b00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f7105073c7a5ab65f92ce95cff02b439a3c6e65550c3ded34090c2152726ad4 0.600000000000 1445660 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": 985459, "vin": [ { "gen": { "height": 985449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f7105073c7a5ab65f92ce95cff02b439a3c6e65550c3ded34090c2152726ad4" } } ], "extra": [ 1, 243, 212, 181, 126, 41, 220, 192, 242, 137, 85, 247, 46, 134, 168, 73, 177, 122, 253, 92, 58, 95, 66, 219, 215, 122, 212, 220, 66, 53, 155, 53, 176, 2, 17, 0, 0, 0, 4, 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