Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c02947261eb641fdcbf551f07d80faf3b5753227721384ce7fe6c55ead1bd8c

Tx prefix hash: 3b5f3535e5b34c458a1581ed739782ca60225ef63729a1bf7c58795a98d74dce
Tx public key: 3bcf6c8dbac3d655c283a1c087a9fd675c4604f882387086a391b6cf7eb6a42e
Timestamp: 1731208895 Timestamp [UCT]: 2024-11-10 03:21:35 Age [y:d:h:m:s]: 00:129:07:04:13
Block: 1150402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92238 RingCT/type: yes/0
Extra: 013bcf6c8dbac3d655c283a1c087a9fd675c4604f882387086a391b6cf7eb6a42e021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf6d4102447162de4772faca51b12a49df46ef967b3a018b043f21d3d346f20e 0.600000000000 1635703 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": 1150412, "vin": [ { "gen": { "height": 1150402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf6d4102447162de4772faca51b12a49df46ef967b3a018b043f21d3d346f20e" } } ], "extra": [ 1, 59, 207, 108, 141, 186, 195, 214, 85, 194, 131, 161, 192, 135, 169, 253, 103, 92, 70, 4, 248, 130, 56, 112, 134, 163, 145, 182, 207, 126, 182, 164, 46, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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