Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a9889d269fae24b95d635ef550e305fef56b8402ff95e9474cf7c003e30dc4

Tx prefix hash: 62aa8f95f4b23ad6d389232778ab273d0c0e47534e0e1c3fb800b6d4dfbb1e4c
Tx public key: 0285c5889ec97a76e96047dba67f6bf77896c77c3743ec1d11d59b29219b7e3f
Timestamp: 1739318380 Timestamp [UCT]: 2025-02-11 23:59:40 Age [y:d:h:m:s]: 00:281:05:25:44
Block: 1217280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198752 RingCT/type: yes/0
Extra: 010285c5889ec97a76e96047dba67f6bf77896c77c3743ec1d11d59b29219b7e3f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5264142a739c382a6d25f879997e178b3f3c0eb6236403b7b2974c426b9b9e5 0.600000000000 1704089 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": 1217290, "vin": [ { "gen": { "height": 1217280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5264142a739c382a6d25f879997e178b3f3c0eb6236403b7b2974c426b9b9e5" } } ], "extra": [ 1, 2, 133, 197, 136, 158, 201, 122, 118, 233, 96, 71, 219, 166, 127, 107, 247, 120, 150, 199, 124, 55, 67, 236, 29, 17, 213, 155, 41, 33, 155, 126, 63, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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