Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb62e31ae9e08306bb303ea70cd52b5440d2b112805f4e12011cbd53ba9b731

Tx prefix hash: ce5587b36916a0786c39d2e0f842faa770b61747d80f9397093c33c59095946e
Tx public key: bed82ca37c95bbe9bbbcf6bce19122fe1f1e9a257b7077a7b44e9eddf98c8c68
Timestamp: 1736606008 Timestamp [UCT]: 2025-01-11 14:33:28 Age [y:d:h:m:s]: 00:112:08:17:55
Block: 1195083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80087 RingCT/type: yes/0
Extra: 01bed82ca37c95bbe9bbbcf6bce19122fe1f1e9a257b7077a7b44e9eddf98c8c680211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de47550a64df2be78dc6a5ac0bd058d1cd55df55b3a0add43052ee095b440ea2 0.600000000000 1681668 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": 1195093, "vin": [ { "gen": { "height": 1195083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de47550a64df2be78dc6a5ac0bd058d1cd55df55b3a0add43052ee095b440ea2" } } ], "extra": [ 1, 190, 216, 44, 163, 124, 149, 187, 233, 187, 188, 246, 188, 225, 145, 34, 254, 31, 30, 154, 37, 123, 112, 119, 167, 180, 78, 158, 221, 249, 140, 140, 104, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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