Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad38217b4ab1be45cb7b68cde16c48712310cbd3dfe34ddea2527521627af5d

Tx prefix hash: d7b88368c608bfeb3901251e783d07a43c7f8d56dfbf98610fdaad1baf976a5a
Tx public key: f393b3b629f9e2ac6f636729dc720f3824479d500b7a30848e3be9dcf4a8f227
Timestamp: 1727536802 Timestamp [UCT]: 2024-09-28 15:20:02 Age [y:d:h:m:s]: 00:056:22:10:33
Block: 1120051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40662 RingCT/type: yes/0
Extra: 01f393b3b629f9e2ac6f636729dc720f3824479d500b7a30848e3be9dcf4a8f227021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ab54f1626268bb426f6aa3ac197a31334f9774ce10e69d4e6e426e3bcb139e7 0.600000000000 1601828 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": 1120061, "vin": [ { "gen": { "height": 1120051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ab54f1626268bb426f6aa3ac197a31334f9774ce10e69d4e6e426e3bcb139e7" } } ], "extra": [ 1, 243, 147, 179, 182, 41, 249, 226, 172, 111, 99, 103, 41, 220, 114, 15, 56, 36, 71, 157, 80, 11, 122, 48, 132, 142, 59, 233, 220, 244, 168, 242, 39, 2, 17, 0, 0, 0, 2, 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