Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28913adbb4d6291ca24970c4c0b511bd543e6b9cbe26b60d77d9d43d7305487e

Tx prefix hash: 11a0d5bc31e84077b000bd8b1c91c1da6c2c7a83e0d01143e1b44c88f7d228bf
Tx public key: 3aa3471973e2e183f469992167de29370854709a48af3e0c8413d74ea2bfc3d5
Timestamp: 1735155042 Timestamp [UCT]: 2024-12-25 19:30:42 Age [y:d:h:m:s]: 00:102:03:44:38
Block: 1183080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72779 RingCT/type: yes/0
Extra: 013aa3471973e2e183f469992167de29370854709a48af3e0c8413d74ea2bfc3d50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2d86823eec750ea78de1f68b9da45aa6370a6088c7aa228df84e4499974e7b 0.600000000000 1669521 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": 1183090, "vin": [ { "gen": { "height": 1183080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2d86823eec750ea78de1f68b9da45aa6370a6088c7aa228df84e4499974e7b" } } ], "extra": [ 1, 58, 163, 71, 25, 115, 226, 225, 131, 244, 105, 153, 33, 103, 222, 41, 55, 8, 84, 112, 154, 72, 175, 62, 12, 132, 19, 215, 78, 162, 191, 195, 213, 2, 17, 0, 0, 0, 6, 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