Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d420ebb46697a1842cd32e09918034c87a222daf178fb3c6052e8d1432534330

Tx prefix hash: 6905c6958943a1dcb51bd48c8153f26eaff6f3ef81df10c1ccb0f91cee4968a0
Tx public key: 59b8e4189c67996de8acb9c5e42380e730245f4d0c6777cf44299ea24caa1ee3
Timestamp: 1695020198 Timestamp [UCT]: 2023-09-18 06:56:38 Age [y:d:h:m:s]: 01:163:05:45:26
Block: 850647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377735 RingCT/type: yes/0
Extra: 0159b8e4189c67996de8acb9c5e42380e730245f4d0c6777cf44299ea24caa1ee30211000000044b8f5122000000000000000000

1 output(s) for total of 0.932080504000 dcy

stealth address amount amount idx
00: 74f336361fe3e52724a7e27a5b315d48b9b6bb56f8ded829cd66fbf070ee68d0 0.932080504000 1304379 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": 850657, "vin": [ { "gen": { "height": 850647 } } ], "vout": [ { "amount": 932080504, "target": { "key": "74f336361fe3e52724a7e27a5b315d48b9b6bb56f8ded829cd66fbf070ee68d0" } } ], "extra": [ 1, 89, 184, 228, 24, 156, 103, 153, 109, 232, 172, 185, 197, 228, 35, 128, 231, 48, 36, 95, 77, 12, 103, 119, 207, 68, 41, 158, 162, 76, 170, 30, 227, 2, 17, 0, 0, 0, 4, 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