Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63ad9791727d28df6cf744387c39fd5e9c1d9971ae3f6d255630fe2880423271

Tx prefix hash: fc14e62b8aaf71e4652203ff660d683ab8c5855f7a9989cf388e15658a63fd10
Tx public key: 193f98a8c1d51658f8a6030652789d2540785e3d165e2118553fb66221a6f4b6
Timestamp: 1708761276 Timestamp [UCT]: 2024-02-24 07:54:36 Age [y:d:h:m:s]: 01:046:07:03:00
Block: 964383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294108 RingCT/type: yes/0
Extra: 01193f98a8c1d51658f8a6030652789d2540785e3d165e2118553fb66221a6f4b602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee915cb41a34588e15a2f9d1fb81c7d9f097cb4c044d2bd97a6f1cbc51c82ce 0.600000000000 1424114 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": 964393, "vin": [ { "gen": { "height": 964383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee915cb41a34588e15a2f9d1fb81c7d9f097cb4c044d2bd97a6f1cbc51c82ce" } } ], "extra": [ 1, 25, 63, 152, 168, 193, 213, 22, 88, 248, 166, 3, 6, 82, 120, 157, 37, 64, 120, 94, 61, 22, 94, 33, 24, 85, 63, 182, 98, 33, 166, 244, 182, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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