Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7661d7e5f35208ef83cd7d1fde6bb623f214777f9c17f3293f469432e4253c6d

Tx prefix hash: b41f1c54b4a094cfc17cb5ff33124c9528c8845d2fcc919f8537901db14b568e
Tx public key: cff385aada87c896d5edb724bad2101b7431064e0db9a5a381e01bf8d47efab2
Timestamp: 1671560857 Timestamp [UCT]: 2022-12-20 18:27:37 Age [y:d:h:m:s]: 02:173:03:58:20
Block: 656858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645498 RingCT/type: yes/0
Extra: 01cff385aada87c896d5edb724bad2101b7431064e0db9a5a381e01bf8d47efab2021100000005faf35c9c000000000000000000

1 output(s) for total of 4.088431707000 dcy

stealth address amount amount idx
00: cf1c642ca8e280789e4d167cb4706a82da3698e928eee4ecd785b0aec7f36804 4.088431707000 1097485 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": 656868, "vin": [ { "gen": { "height": 656858 } } ], "vout": [ { "amount": 4088431707, "target": { "key": "cf1c642ca8e280789e4d167cb4706a82da3698e928eee4ecd785b0aec7f36804" } } ], "extra": [ 1, 207, 243, 133, 170, 218, 135, 200, 150, 213, 237, 183, 36, 186, 210, 16, 27, 116, 49, 6, 78, 13, 185, 165, 163, 129, 224, 27, 248, 212, 126, 250, 178, 2, 17, 0, 0, 0, 5, 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