Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d2953979394f5cb6cc2683a025a451a1371e6be417ac734d78779f5539ee68

Tx prefix hash: ab19ed2508c377480479a6308b46b31dfd2f9c1d262b02f12dd318b9280c60bc
Tx public key: 22164c1dd7806f77b08c75f1ae0ff001d9c06df24de8cc7c2d1caa7cecf42b72
Timestamp: 1722107851 Timestamp [UCT]: 2024-07-27 19:17:31 Age [y:d:h:m:s]: 00:247:00:42:06
Block: 1075031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176456 RingCT/type: yes/0
Extra: 0122164c1dd7806f77b08c75f1ae0ff001d9c06df24de8cc7c2d1caa7cecf42b72021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e74a388e71bcea5eee5c15b6753277dd0d50b0a4b3cf97a9f3bc3c30363f0212 0.600000000000 1547550 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": 1075041, "vin": [ { "gen": { "height": 1075031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e74a388e71bcea5eee5c15b6753277dd0d50b0a4b3cf97a9f3bc3c30363f0212" } } ], "extra": [ 1, 34, 22, 76, 29, 215, 128, 111, 119, 176, 140, 117, 241, 174, 15, 240, 1, 217, 192, 109, 242, 77, 232, 204, 124, 45, 28, 170, 124, 236, 244, 43, 114, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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