Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be248cf899d4641524299893c00221de13664388b3a3b0d6a00e7ebe24cf54a7

Tx prefix hash: c1c9d7a8c47cd046b79885ba7cde28ee45ae0bde66c8f3d0ba5eb10fc65ee8c5
Tx public key: dd0083155aa6655c9bced97ecb624e0a5b711318ab5a36d38e15ba6af8f24835
Timestamp: 1700941959 Timestamp [UCT]: 2023-11-25 19:52:39 Age [y:d:h:m:s]: 01:054:10:46:30
Block: 899553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300314 RingCT/type: yes/0
Extra: 01dd0083155aa6655c9bced97ecb624e0a5b711318ab5a36d38e15ba6af8f248350211000000014b8f5122000000000000000000

1 output(s) for total of 0.641811468000 dcy

stealth address amount amount idx
00: 58b0a7c782d76b905e686d11513297f75a74e0864bd5e66b9344a69c86779639 0.641811468000 1356012 of 0

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": 899563, "vin": [ { "gen": { "height": 899553 } } ], "vout": [ { "amount": 641811468, "target": { "key": "58b0a7c782d76b905e686d11513297f75a74e0864bd5e66b9344a69c86779639" } } ], "extra": [ 1, 221, 0, 131, 21, 90, 166, 101, 92, 155, 206, 217, 126, 203, 98, 78, 10, 91, 113, 19, 24, 171, 90, 54, 211, 142, 21, 186, 106, 248, 242, 72, 53, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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