Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e75df151b3a8a7eaf0c33bcc2556a59ce6491c25da2fbefe9e538834535db57

Tx prefix hash: 152b10f7e86feaa4a723d762c6dd3ab89401e52196c3cde5543f7038848fbf15
Tx public key: fa8c1ddc1385f4ece8ac65864a562045fc2879318d7bf3a932a8d0c891b196e4
Timestamp: 1682576813 Timestamp [UCT]: 2023-04-27 06:26:53 Age [y:d:h:m:s]: 01:344:11:35:44
Block: 747549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507457 RingCT/type: yes/0
Extra: 01fa8c1ddc1385f4ece8ac65864a562045fc2879318d7bf3a932a8d0c891b196e4021100000001faf35c9c000000000000000000

1 output(s) for total of 2.046747606000 dcy

stealth address amount amount idx
00: c6fd489ff39e71b3dad8ac5628bdbe50e58c6299b8fb294d6f2dcfe4b6bb934b 2.046747606000 1195234 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": 747559, "vin": [ { "gen": { "height": 747549 } } ], "vout": [ { "amount": 2046747606, "target": { "key": "c6fd489ff39e71b3dad8ac5628bdbe50e58c6299b8fb294d6f2dcfe4b6bb934b" } } ], "extra": [ 1, 250, 140, 29, 220, 19, 133, 244, 236, 232, 172, 101, 134, 74, 86, 32, 69, 252, 40, 121, 49, 141, 123, 243, 169, 50, 168, 208, 200, 145, 177, 150, 228, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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