Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d2fd0ef92cd3fb3f5aff68cce39e9bbdcfbb0e95f9ae39c4378129577c1272

Tx prefix hash: 7eee4b5a4dcc9c33d80e0e79a7e947f7ac5300a67833ce98a4e6b20147e0eb2b
Tx public key: a9b767929714cff0a74a07b2e45af03a112e546ba8bfb7c3cfecac6478f61632
Timestamp: 1729127349 Timestamp [UCT]: 2024-10-17 01:09:09 Age [y:d:h:m:s]: 00:148:14:26:41
Block: 1133230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105984 RingCT/type: yes/0
Extra: 01a9b767929714cff0a74a07b2e45af03a112e546ba8bfb7c3cfecac6478f616320211000000063cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b08f7b840bc5990170104eebaef853bd76b2b97270b58471e8064afdf87c9f0d 0.600000000000 1616307 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": 1133240, "vin": [ { "gen": { "height": 1133230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b08f7b840bc5990170104eebaef853bd76b2b97270b58471e8064afdf87c9f0d" } } ], "extra": [ 1, 169, 183, 103, 146, 151, 20, 207, 240, 167, 74, 7, 178, 228, 90, 240, 58, 17, 46, 84, 107, 168, 191, 183, 195, 207, 236, 172, 100, 120, 246, 22, 50, 2, 17, 0, 0, 0, 6, 60, 208, 252, 6, 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