Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34afda20820284f77b501d00baf65635c83a9b6495e07206e5c22694d72ad1d5

Tx prefix hash: bca3fd14037fc89aee95368f33ecdc2b0fc10573c849a6205ee2e2bd2c364506
Tx public key: 3e93738f1c1beba85458d64e197a50d8c1f6bab6bc41d095df223edeeb000c9e
Timestamp: 1709099090 Timestamp [UCT]: 2024-02-28 05:44:50 Age [y:d:h:m:s]: 01:057:14:03:32
Block: 967189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302180 RingCT/type: yes/0
Extra: 013e93738f1c1beba85458d64e197a50d8c1f6bab6bc41d095df223edeeb000c9e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0830561af9eae4ec83a245c62f5ac139826322f4b97d17f4d943331a4b49cb8e 0.600000000000 1426960 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": 967199, "vin": [ { "gen": { "height": 967189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0830561af9eae4ec83a245c62f5ac139826322f4b97d17f4d943331a4b49cb8e" } } ], "extra": [ 1, 62, 147, 115, 143, 28, 27, 235, 168, 84, 88, 214, 78, 25, 122, 80, 216, 193, 246, 186, 182, 188, 65, 208, 149, 223, 34, 62, 222, 235, 0, 12, 158, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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