Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da3974de38c09a3a3590c6e468e044d29ed8f8fef0d9efd4bd1cd62b0c14cbb6

Tx prefix hash: cc7f81ba7bb75bc7014143a13a5423b945550393bc68b4c7081440c32eff6b3c
Tx public key: 65241b43d8cca76d62e1031e0da391fdd2fd00f3701a4b002836585dd8dc12d7
Timestamp: 1728196166 Timestamp [UCT]: 2024-10-06 06:29:26 Age [y:d:h:m:s]: 00:174:08:20:23
Block: 1125509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124394 RingCT/type: yes/0
Extra: 0165241b43d8cca76d62e1031e0da391fdd2fd00f3701a4b002836585dd8dc12d702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad0e2a0145bfd9a6a91dd6bca9b292e0ff76d5ce26f807cb3429ba5d897bee10 0.600000000000 1608260 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": 1125519, "vin": [ { "gen": { "height": 1125509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad0e2a0145bfd9a6a91dd6bca9b292e0ff76d5ce26f807cb3429ba5d897bee10" } } ], "extra": [ 1, 101, 36, 27, 67, 216, 204, 167, 109, 98, 225, 3, 30, 13, 163, 145, 253, 210, 253, 0, 243, 112, 26, 75, 0, 40, 54, 88, 93, 216, 220, 18, 215, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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