Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbb963ae22250efaf0535546afa8714f8d6908981a7b3d307688dc2b57b86d7

Tx prefix hash: 964a7cfa7bd62c75730e062496a09508dd37c0e76015fbaeda8aba5443381545
Tx public key: 5a037c9ca6cf5446725a47eee56e93d650f390865799c79b3e934bccde4a4dc3
Timestamp: 1704912564 Timestamp [UCT]: 2024-01-10 18:49:24 Age [y:d:h:m:s]: 01:139:03:30:20
Block: 932457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360593 RingCT/type: yes/0
Extra: 015a037c9ca6cf5446725a47eee56e93d650f390865799c79b3e934bccde4a4dc302110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48b1bc1d8ab993bb6ab0a1e2a88d78dcb9abbe2091098cd5c0b02f129087c15e 0.600000000000 1390393 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": 932467, "vin": [ { "gen": { "height": 932457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48b1bc1d8ab993bb6ab0a1e2a88d78dcb9abbe2091098cd5c0b02f129087c15e" } } ], "extra": [ 1, 90, 3, 124, 156, 166, 207, 84, 70, 114, 90, 71, 238, 229, 110, 147, 214, 80, 243, 144, 134, 87, 153, 199, 155, 62, 147, 75, 204, 222, 74, 77, 195, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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